Requirements for Contributing to this repository

• Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
• The pull request must only fix one issue, or add one feature, at the time.
• The pull request must update the test suite to demonstrate the changed functionality.
• After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see CONTRIBUTING.

What does this PR do?

This experimental feature allows the user to limit the number of samples per context for histogram, distribution, and timing metrics.

This can be enabled with the statsd_max_samples_per_context flag. When enabled up to n samples will be kept in per context for Histogram, Distribution and Timing metrics when Aggregation is enabled. The default value is 0 which means no limit.

This is already implemented for the go client. Go Client Docs

Description of the Change

Verification Process

For local testing, follow steps here to set up local testing for the python client

Replace testapp/main.py with

from datadog import initialize, statsd
import time


options = {
    "statsd_host": "127.0.0.1",
    "statsd_port": 8125,
    "statsd_disable_buffering" : True,
    "statsd_disable_aggregation" : False,
    "statsd_max_samples_per_context" : 1,
    "statsd_aggregation_flush_interval" : 15
}

initialize(**options)

x = 0
name = "andrew_q_maxsample2"
sleepTime = 3
while(1):
  print("-------------------------------------------------")
  print("running :)", x)
  statsd.histogram(name, 1)
  time.sleep(sleepTime)
  x += 1

Additional Notes

Release Notes

Review checklist (to be filled by reviewers)

• Feature or bug fix MUST have appropriate tests (unit, integration, etc...)
• PR title must be written as a CHANGELOG entry (see why)
• Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
• PR must have one changelog/ label attached. If applicable it should have the backward-incompatible label attached.
• PR should not have do-not-merge/ label attached.
• If Applicable, issue must have kind/ and severity/ labels attached at least.